Auto-Generated Summary

> Provide an extensive summary of the agreements by topic. No need to mention CRs.

Extensive Summary of Agreements by Topic

UE UAV Beamforming Capabilities for FR1

• Directional Antennas: RAN1 will only consider potential UE UAV beamforming capabilities for FR1 with directional antennas in Rel-18 if such capabilities do not impact RAN4 requirements.
• Baseline Framework: If new UE UAV beamforming capabilities for FR1 are supported, the Rel-17 unified TCI framework will be considered as the baseline.
• Multi-TRP Beamforming: Multi-TRP beamforming is not supported for UAV UEs in FR1 in Rel-18.

Beam Switching Among Fixed Directional Antennas

• Support: UE UAV beamforming for FR1 based on beam switching among fixed directional antennas is supported in Rel-18.
• Note 1: New UE capabilities may not be necessary to support beam switching among fixed directional antennas.
• Note 2: No RAN4 specification impact is assumed.
• FFS: Whether updating legacy UE capabilities (e.g., extending to FR1) is needed, and it is not precluded if necessary.
• FFS: Whether/how specifications may be impacted.

Beam Correspondence

• Definition: Beam correspondence for a UE UAV operating in FR1 (if introduced) based on fixed directional antennas would not require radiated requirements in RAN4. Beam correspondence means the UE uses the same fixed directional antenna for transmitting and receiving.

Use Case for Beam Switching

• Identified Use Case: Beam switching among fixed directional antennas is identified as a use case to limit interference and balance traffic load to adjacent cells.

Legacy Framework Limitations

• Network Awareness: Without new UE capability, using the legacy BM/SRI framework, the network cannot be aware whether a UAV UE is using fixed directional antennas or omnidirectional antennas.
• Note: It is not necessarily required or beneficial for the network to be aware of the type of antenna used by a UAV UE.

Reporting of Beamforming Capabilities

• Consensus: There is no consensus on whether new UE UAV capabilities, including beam-related information, beam correspondence, or QCL Type-D, should be reported.
• Sufficiency: Uncertainty remains on whether reporting UE UAV beamforming capabilities alone is sufficient to support beamforming based on beam switching among fixed directional antennas to limit interference and/or balance traffic load to adjacent cells in FR1 in Rel-18.

Additional Studies

• Beam Characteristics: Study the indication of beam characteristics (e.g., number of beams, beamwidth, beam center, radiated EIRP) as UAV UE capability.
• FFS: Feasibility/benefit of indicating beam orientation, including height dependence.
• FFS: Necessary parameters, suitable value ranges, and methods of indication.
• FFS: Indication of beams as either ‘fixed’ or ‘adaptive.’
• Minimum Beam Application Latency: Study the indication of minimum beam application latency as UAV UE capability.
• UnifiedJointTCI-r17: If supported, determine suitable range of values for minBeamApplicationTime-r17.
• Enhancements: If UnifiedJointTCI-r17 is not supported, consider enhancements to timedurationforQCL.
• FFS: Additional parameters, e.g., beamSwitchTiming.

General Notes

• Whether to specify parameters depends on:
• Identification of target scenarios and potential issues faced by UAVs.
• Assessment of existing capabilities, mechanisms, and frameworks as candidates to address these issues.
• Necessity of specifying new parameters (i.e., whether existing solutions can already address the issues).

This summary consolidates the agreements and discussions across various sessions and contributions related to UAV beamforming capabilities in Rel-18.